Release 10.1A: OpenEdge Application Server:
Administration

WebSpeed configuration overview

You must perform the following preliminary tasks before you can begin configuring the WebSpeed installation:

Install the necessary WebSpeed components. You can distribute WebSpeed components over a number of machines, but the WebSpeed Messenger must be installed in the scripts directory of your Web server.
Configure the machines involved in the WebSpeed installation. This includes setting the appropriate environment variables and setting up your Web server.

For more information about these preliminary tasks, see OpenEdge Getting Started: Installation and Configuration .

Once you complete these preliminary tasks, you can begin to configure the WebSpeed components.

To configure the WebSpeed components:

Start the AdminServer process on each machine by using the PROADSV utility. (See the "Starting the AdminServer" section.)
Once the AdminServer is running, you can then use the Progress Explorer or a text editor to create and modify NameServer and WebSpeed Transaction Server configurations. These configurations are in the properties file (ubroker.properties) on the machine where you installed the WebSpeed Transaction Server. You can use the Progress Explorer remotely from a Windows machine to access configurations installed on a UNIX machine.

You can also edit the ubroker.properties file manually using a text editor. If you choose to use a text editor, you must have file system access to the file. (See the "Overview of the ubroker.properties file" section.)

Note: You can use the mergeprop utility installed with OpenEdge to manually edit the ubroker.properties file. For information on using mergeprop, see OpenEdge Getting Started: Installation and Configuration .

You can validate NameServer and WebSpeed configurations using the validation utilities, NSCONFIG and WSCONFIG. These utilities must have access to the properties file. (See the "NSCONFIG" section and the "WSCONFIG" section.)

Determine if you need to set (or change any preset) WebSpeed environment variables. (See the "Setting up the WebSpeed environment" section.)
Use the NSMAN utility (or the Progress Explorer remotely) to start up a NameServer instance that you configured to coordinate client access to one or more WebSpeed Transaction Server instances on your network. After the NameServer has started, use the WTBMAN utility (or the Progress Explorer remotely) to start up each WebSpeed Transaction Server instance controlled by that NameServer. (See the "Starting the WebSpeed Transaction Server and NameServer" section.)

After a WebSpeed Transaction Server starts up, it registers its location and the Application Services it supports with its controlling NameServer.

Set up the WebSpeed Messenger on your Web server. (See the "Setting up WebSpeed on the Web server machine" section.)
At any time after Step 5, you can validate that the AdminServer, the NameServer, and the WebSpeed Transaction Server are running and test the configuration to confirm that you have set up WebSpeed correctly. You perform this validation by using the WebSpeed command-line utilities, the Progress Explorer (remotely from a Windows machine), or the WebSpeed Messenger Administration (WSMAdmin) page in a browser. (See the "Testing your configuration" section for more information.)
You can shut down the AdminServer process at any time on the WebSpeed machine. If you shut down the AdminServer while there are NameServer and WebSpeed Transaction Server instances still running, those instances are shut down as well.